Prototype Apple container sidecar torch frontend#144
Merged
Conversation
2714624 to
b7bfe52
Compare
b7bfe52 to
5cda063
Compare
5cda063 to
f02a651
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
lupine.sidecar(...)frontend that launches a Linux/arm64 PyTorch worker through Applecontaineron macOScontainerinstallsTorchDispatchModeinstead of per-op Python boilerplateValidation
uv run pytestuv run --python 3.13 --with pytest --with torch --with numpy --with-editable ./python pytest -q python/tests/test_lupine_adapter.pylupine-pytorch-worker:cuda-13.1.0with Apple container[0.0, 2.0, 4.0, 6.0, 8.0, 10.0, 12.0, 14.0]through sidecar CUDA PyTorch on an RTX 4090Notes
This is intentionally a prototype backend. It proves the local macOS frontend plus Linux sidecar approach, but there are still CUDA backend limitations outside the Python forwarding layer.